If this value is 0, disable log file truncation during creation of new database snapshots. If this value is 1 (default), enable truncation. See Configuring the MaximumLogSize setting.

The path of the vault database file if Hypertrieve is used.

Path of the SQL Server data files used by this vault.

If SQL Server or Oracle support is installed, this value will be used as a base name for locally generated files. It will also be used as a database name for Microsoft-SQL Server and as a source to generate table names for Oracle.

The amount of time in minutes the database cache will remain in memory after all users have logged out of the system. Only used in very specific situations. The default is 5.

Name of the database engine DLL file that serves this vault: ObjectSet.dll, ObjectSetORA.dll, ObjectSetSQL.dll, or ht3.dll (64-bit only).

See About the High Performance Option.

Size of individual extended memory blocks used by the High Performance Option. The default size is 1 KB.

Number of individual extended memory blocks used by the High Performance Option. Set in Meridian Administrator as described in About the High Performance Option.

On 64-bit computers, if this value is 1 (default) or missing, vaults are loaded completely into cache memory and a cache file (.CHE) is not created between EDM Server sessions. To force the creation of cache files, use the AlwaysCreateCheFile setting.

If this value is 0, vaults are loaded into cache memory according to the vault's cache settings.

If this value is 0 (default), when an unsuccessful database shutdown is detected, the database engine normally restores the database by playing the log file against the existing snapshot. If this value is >0, the engine does not restore the database from snapshot after unsuccessful shutdown and continues with the database, which probably contains inconsistencies.

Path of the SQL Server index files used by this vault. If empty, uses DataPath value.

Name of the Oracle server instance used by this vault.

If this value is 1, the Oracle instance is hosted on the local computer. If this value is 0, the Oracle instance is hosted on a remote computer.

Path to be used for locally created SQL Server files. If empty, DataPath will be used.

Server performance option for use with SQL Server. See Integrating Meridian with SQL Server.

Path of the SQL Server transaction log files used by this vault. If empty, uses DataPath value.

Server performance option. See Optimizing the Meridian server software. and Configuring the MaximumCacheSize setting.

When the snapshot period has expired and the log file size is greater than this value, a new snapshot will be created and the existing log file will be truncated. Server performance option. See Optimizing the Meridian server software. and Configuring the MaximumLogSize setting.

Server performance option for use with SQL Server. See Integrating Meridian with SQL Server.

Timeout in minutes after which log truncation will be attempted. Default = 240. Server performance option. See Optimizing the Meridian server software.

Server performance option. See Optimizing the Meridian server software and Configuring the RelativeCacheSize setting.

Server performance option for use with SQL Server. See Integrating Meridian with SQL Server.

Name of the Oracle schema used by this vault.

Name of the computer running SQL Server that hosts this vault. Empty for default server located on local server.

Obsolete

Full local path to the trace file. If this value is not present, no trace file will be written. See Reviewing the server configuration information.

If this value is >0 and TraceName is set, activates tracing of all calls to the database engine. This reduces server performance by approximately 50%.  See Reviewing the server configuration information.

For future use.